Adaptive load balancing

ABSTRACT

In an example, there is provided a network apparatus for providing native load balancing within a switch, including a first network interface operable to communicatively couple to a first network; a plurality of second network interfaces operable to communicatively couple to a second network, the second network comprising a service pool of service nodes; one or more logic elements providing a switching engine operable for providing network switching; and one or more logic elements comprising a load balancing engine operable for: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration; detecting a new service node added to the service pool; and adjusting the load balancing configuration to account for the new service node; wherein the switching engine and load balancing engine are configured to be provided on the same hardware as each other and as the first network interface and plurality of second network interfaces.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application 62/152,022, filed Apr. 23, 2015, titled “Method and Apparatus for Adaptive Load Balancing in Automated Fabrics,” which is incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

This disclosure relates in general to the field of communications and, more particularly, to a method and apparatus for providing adaptive load balancing on a network switch.

BACKGROUND

Data centers are increasingly used by enterprises for effective collaboration, data storage, and resource management. A typical data center network contains myriad network elements including servers, load balancers, routers, switches, etc. The network connecting the network elements provides secure user access to data center services and an infrastructure for deployment, interconnection, and aggregation of shared resources. Improving operational efficiency and optimizing utilization of resources in data centers are some of the challenges facing data center managers. Data center managers seek a resilient infrastructure that consistently supports diverse applications and services. A properly planned data center network provides application and data integrity and, further optimizes application availability and performance.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is best understood from the following detailed description when read with the accompanying figures. It is emphasized that, in accordance with the standard practice in the industry, various features are not necessarily drawn to scale, and are used for illustration purposes only. Where a scale is shown, explicitly or implicitly, it provides only one illustrative example. In other examples, the dimensions of the various features may be arbitrarily increased or reduced for clarity of discussion.

FIG. 1A is a network level diagram of an enterprise computing environment according to one or more examples of the present Specification;

FIG. 1B is a more detailed view of a computing cluster according to one or more examples of the present Specification;

FIG. 2A is a simplified schematic diagram illustrating a physical view of a system for providing service appliances in a network environment according to one or more examples of the present Specification;

FIG. 2B is a simplified schematic diagram illustrating a logical view of the system according to one or more examples of the present Specification;

FIG. 3 is a block diagram of a network switch according to one or more examples of the present Specification.

FIG. 4 is a block diagram of a routing table according to one or more examples of the present Specification.

FIG. 5 is a flow chart of a method performed by a switch according to one or more examples of the present Specification.

FIG. 6 is a flow chart of a method of load balancing according to one or more examples of the present Specification.

FIG. 7 is a block diagram of a method according to one or more examples of the present Specification.

FIG. 8 is a block diagram of a leaf-spine architecture according to one or more examples of the present Specification.

FIG. 9 is a flow chart of a method of configuring adaptive load balancing according to one or more examples of the present Specification.

FIG. 10 is a flow chart of a method of adding a new node in adaptive load balancing according to one or more examples of the present Specification.

FIG. 11 is a flow chart of a method of removing a node in adaptive load balancing according to one or more examples of the present Specification.

SUMMARY

In an example, there is provided a network apparatus for providing native load balancing within a switch, including a first network interface operable to communicatively couple to a first network; a plurality of second network interfaces operable to communicatively couple to a second network, the second network comprising a service pool of service nodes; one or more logic elements providing a switching engine operable for providing network switching; and one or more logic elements comprising a load balancing engine operable for: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration; detecting a new service node added to the service pool; and adjusting the load balancing configuration to account for the new service node; wherein the switching engine and load balancing engine are configured to be provided on the same hardware as each other and as the first network interface and plurality of second network interfaces.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following disclosure provides many different embodiments, or examples, for implementing different features of the present disclosure.

In an example of a known computing system, a cluster of workload servers may be provisioned, either as physical servers or as virtual machines, to provide a desired feature to end-users or clients. To provide just one nonlimiting example, the workload servers may provide a website. When a plurality of users make a large number of simultaneous connections to the website, it is necessary to appropriately distribute the workload among the various servers in the server farm.

To this end, incoming traffic from client devices may be routed to a network switch. The network switch may then forward the traffic to a load balancer. An example of a commonly used load balancer is a network appliance or virtual appliance running a Linux operating system and provided with a full network stack, as well as load-balancing logic for determining which server to send the traffic to.

For example, a workload cluster may include 16 nodes, either physical servers or virtual machines. The load balancer itself may also be either a physical appliance or a virtual appliance. Upon receiving a packet, the load balancer determines the load on each of the 16 workload servers. The load balancer then applies an algorithm to determine an appropriate node for handling the traffic. This may include, for example, identifying a least burdened node and assigning the traffic to that node. Each node may have its own IP address, which in one embodiment is not exposed to end-user client devices. Rather, client devices are aware only of the IP address of the load balancer itself. Thus, the load balancer may modify the packet header, for example, by assigning it to the virtual IP (VIP) of one of the workload servers. The load balancer may then return the packet to the switch, which routes the packet to the appropriate workload server.

In this example, the incoming packet transfers from the switch to the load balancer, which may provide the full OSI 7 layer “stack” in software, operating on a full-featured operating system, such as Linux. Thus, the incoming packet is abstracted up to one of the upper layers of the OSI model, such as layer 6 or 7, so that it can be handled by the load-balancing software. The packet is then de-abstracted to a lower layer and returned to the switch, which forwards it to the appropriate workload server. Upon receiving the packet, the workload server again abstracts the packet up to one of the higher levels of the OSI model.

The inventors of the present Specification have recognized that the load balancer, and its overhead, represents a potential bottleneck that reduces the scalability of the network environment, and slows down handling of network traffic. The process of passing the packet up and down the OSI stack, in particular, while very fast from a human point of view, can be a significant bottleneck from the point of view of a network.

However, the named inventors of the present application have recognized that a network device, such as a switch or a router, can be configured to natively act as a load balancer in addition to performing its ordinary network switching function. In that case, rather than provide a load-balancing algorithm in an application running on an operating system, the switch may provide load-balancing via a much faster solution, such as programmable hardware rather than a general purpose software-driven processor. This means that the load-balancing logic is handled mostly or entirely at the hardware level. Furthermore, the switch generally operates at lower levels of the OSI model, such as layers 1 and 2. Thus, it has reduced overhead in abstracting and de-abstracting packets through the OSI stack.

Thus, the switch itself becomes the load balancer, and rather than acting as a bottleneck, is capable of providing terabit-class bandwidth by operating at the hardware level.

In an example, a concept of traffic buckets and nodes is described. Traffic may be divided into “buckets.” Each bucket may be assigned to a node.

A traffic bucket serves as a classifier for identifying a subset of traffic to be redirected. As many traffic buckets can be created as needed for granularity. For bucketization of traffic, various L2/L3 header fields can be used in the algorithm.

By selecting different fields, many buckets can be created. By way of example, we can use B0, B1, B2, B3, B4 . . . Bn to designate traffic buckets.

A traffic node serves as a “next-hop” for traffic forwarding. A node is an entity that has an associated IP address reachable from the switch. By way of example, we can use N0, N1, N2, N3 . . . Nm to designate nodes.

Mapping can be established to associate a traffic bucket to a node. This association creates a packet path for forwarding of traffic for each bucket. This can include one-to-one mapping of a traffic bucket to a node, or many-to-one mapping of traffic buckets to a node (i.e., multiple nodes may be assigned to a single node).

This architecture realizes substantial advantages over certain existing deployments. For example, some existing load balancers suffer from shortcomings such as inefficiency and expense. In one example, a low capacity load-balancer provides approximately 40 Gbps, while a higher-end load balancer provides approximately 200 Gbps.

As discussed above, speed and scalability are enhanced by programming the load balancing engine in programmable hardware rather than in software running on a general-purpose processor programmed by software. Programmable hardware includes, for example, an application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), programmable logic array (PLA), or similar. Because the logic is implemented directly in hardware, it can execute a “program” orders of magnitude faster than a CPU, which must fetch instructions from memory, and then run those instructions on general-purpose hardware. Furthermore, an operating system, multitasking, and multi-layer network stack introduce additional complexity that does not contribute directly to carrying out the load balancing function. In short, a software-programmable CPU is extremely versatile, and its function may be easily adapted to many different tasks, but it is relatively slow. A dedicated programmable hardware device, programmed only for a single function, is not versatile, but carries out its single, dedicated function very quickly.

In one example, a hardware-based load balancer of the present Specification must be able to handle both traffic that is to be load balanced, and traffic that does not require load balancing. For non-load-balanced traffic, the device should still perform its native function as a switch or router, and simply switch or route the traffic as appropriate.

To aid in this, and to preserve the speed advantage of the programmable hardware-based load balancing engine, it is advantageous not to store data values in standard memories such as random access memories (RAM), as this could negate the speed advantages of the hardware. Rather, in one example, a ternary content-addressable memory (TCAM) is provided, and may be capable of operating at speeds approaching the speed of the programmable hardware itself. A content-addressable memory (CAM) is a species of memory used in extremely high-speed searches, such as those necessary for native terabit-class load balancing. CAM compares the search input (tag) to a table of stored data, and returns the address of matching datum. This is in contrast to RAM, in which the program provides an address, and the RAM returns a value stored at that address. When a search is performed, if the CAM finds a match for the tag, the CAM returns the address of the tag, and optionally, the value of the tag as well. If the tag is not found, a “not found” value is returned. TCAM is a species of CAM, in which a tag can be searched not only for a binary “1” or “0,” but also for a ternary “X” (don't care). In other words, the search tag “110X” matches both “1101” and “1100.”

In the context of load balancing, a network administrator may configure a virtual IP (VIP) tag, including in one example an IP address, protocol, and port number. Entries may be made in the TCAM for VIP tags that are to be load balanced. Entries may also be made for a set of nodes that can receive traffic matching that VIP tag.

The switch advertises the VIP tag via routing protocols, and receives traffic destined for VIP. When traffic enters the switch or router, the VIP tag is checked against entries in the TCAM. If there is a matching entry, the traffic is to be load balanced. The traffic is then bucketized and load balanced to each node using TCAM entries.

This architecture realizes several important advantages. As servers move from 1 Gbps to 10 Gbps, traditional software load balancers have to scale appropriately. Load balancer appliances and service modules also consume rack-space, power, wiring and cost. However, in an embodiment of the present Specification:

Every port of a switch or router can act as a load-balancer.

No external appliance and no service module are needed.

The teachings of this Specification can be used to provide terabit-class load balancing.

Embodiments of the present Specification particularly relate to providing adaptive load balancing. Adaptive load balancing may help to deal with issues that arrive within the context of virtualization. More particularly, the benefits of virtualizing servers have recently been a topic of much discussion. However, virtualization also brings new challenges to a data center. One of the advantages of virtualization is dynamic, flexible and efficient deployment of resources. In other words, new VMs can be “spun up” (i.e., provisioned) as needed to meet demand, and then “spun down” (i.e., de-provisioned) once demand falls.

Resources may be distributed by a server load balancer to share workloads. A network administrator may divide responsibilities into various roles such as application, server, or network infrastructure, with different roles being served by different server pools. Within IT organizations, these roles may actually be administered by different individual network administrators. Thus, coordination among internal groups is important. But such coordination may itself be time-consuming and may undermine at least some of the efficiency gains of virtualization. Thus, it is advantageous to streamline workload automation without manual intervention. To this end, the present Specification provides, inter alio, an intelligent traffic director (ITD) as a load balancing feature with host awareness provided, for example, by Cisco® Dynamic Fabric Automation (DFA) capabilities or other similar technology on a network switch. This enables “touchless” configuration of ITD as new nodes are added to or removed from a server pool.

A system and method for adaptive load balancing on a switch will now be described with more particular reference to the attached FIGURES. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. Further, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. Different embodiments many have different advantages, and no particular advantage is necessarily required of any embodiment.

In some embodiments, hyphenated reference numerals, such as 10-1 and 10-2, may be used to refer to multiple instances of the same or a similar item 10, or to different species of a genus 10.

FIG. 1A is a network-level diagram of a secured enterprise 100 according to one or more examples of the present Specification. In the example of FIG. 1, a plurality of users 120 operates a plurality of client devices 110. Specifically, user 120-1 operates desktop computer 110-1. User 120-2 operates laptop computer 110-2. And user 120-3 operates mobile device 110-3.

Each computing device may include an appropriate operating system, such as Microsoft Windows, Linux, Android, Mac OSX, Apple iOS, Unix, or similar. Some of the foregoing may be more often used on one type of device than another. For example, desktop computer 110-1, which in one embodiment may be an engineering workstation, may be more likely to use one of Microsoft Windows, Linux, Unix, or Mac OSX. Laptop computer 110-2, which is usually a portable off-the-shelf device with fewer customization options, may be more likely to run Microsoft Windows or Mac OSX. Mobile device 110-3 may be more likely to run Android or iOS. However, these examples are not intended to be limiting.

Client devices 110 may be any suitable computing devices. In various embodiments, a “computing device” may be or comprise, by way of non-limiting example, a computer, workstation, server, mainframe, embedded computer, embedded controller, embedded sensor, personal digital assistant, laptop computer, cellular telephone, IP telephone, smart phone, tablet computer, convertible tablet computer, computing appliance, network appliance, receiver, wearable computer, handheld calculator, virtual machine, virtual appliance, or any other electronic, microelectronic, or microelectromechanical device for processing and communicating data.

Client devices 110 may be communicatively coupled to one another and to other network resources via enterprise network 170. Enterprise network 170 may be any suitable network or combination of one or more networks operating on one or more suitable networking protocols, including for example, a local area network, an intranet, a virtual network, a wide area network, a wireless network, a cellular network, or the Internet (optionally accessed via a proxy, virtual machine, or other similar security mechanism) by way of nonlimiting example. Enterprise network 170 may also include one or more servers, firewalls, routers, switches, security appliances, antivirus servers, or other useful network devices. In this illustration, enterprise network 170 is shown as a single network for simplicity, but in some embodiments, enterprise network 170 may include a large number of networks, such as one or more enterprise intranets connected to the Internet. Enterprise network 170 may also provide access to an external network, such as the Internet, via external network 172. External network 172 may similarly be any suitable type of network.

A network administrator 150 may operate an administration console 140 to administer a workload cluster 142 and to otherwise configure and enforce enterprise computing and security policies.

Enterprise 100 may encounter a variety of “network objects” on the network. A network object may be any object that operates on or interacts with enterprise network 170. In one example, objects may be broadly divided into hardware objects, including any physical device that communicates with or operates via the network, and software objects. Software objects may be further subdivided as “executable objects” and “static objects.” Executable objects include any object that can actively execute code or operate autonomously, such as applications, drivers, programs, executables, libraries, processes, runtimes, scripts, macros, binaries, interpreters, interpreted language files, configuration files with inline code, embedded code, and firmware instructions by way of non-limiting example. A static object may be broadly designated as any object that is not an executable object or that cannot execute, such as documents, pictures, music files, text files, configuration files without inline code, videos, and drawings by way of non-limiting example. In some cases, hybrid software objects may also be provided, for example, a word processing document with built-in macros or an animation with inline code. For security purposes, these may be considered as a separate class of software object, or may simply be treated as executable objects.

Enterprise security policies may include authentication policies, network usage policies, network resource quotas, antivirus policies, and restrictions on executable objects on client devices 110 by way of non-limiting example. Various network servers may provide substantive services such as routing, networking, enterprise data services, and enterprise applications.

Secure enterprise 100 may communicate across enterprise boundary 104 with external network 172. Enterprise boundary 104 may represent a physical, logical, or other boundary. External network 172 may include, for example, websites, servers, network protocols, and other network-based services. In one example, a wireless base station 130, an external server 180, and an application repository 182 may be provided on external network 172, by way of nonlimiting example. Wireless base station 130 may be, for example, an LTE base station or other similar device that connects to mobile device 110-3 wirelessly. Wireless base station 130 may in turn communicatively couple to external network 172. External server 180 may be a server that provides web pages, data, or other resources that enterprise users 120 may need to use.

Application repository 182 may represent a Windows or Apple “App Store” or update service, a Unix-like repository or ports collection, or other network service providing users 120 the ability to interactively or automatically download and install applications on client devices 110. In some cases, secured enterprise 100 may provide policy directives that restrict the types of applications that can be installed from application repository 182. Thus, application repository 182 may include software that is not malicious, but that is nevertheless against policy. For example, some enterprises restrict installation of entertainment software like media players and games. Thus, even a secure media player or game may be unsuitable for an enterprise computer. Security administrator 150 may be responsible for distributing a computing policy consistent with such restrictions and enforcing it on client devices 120.

In another example, secured enterprise 100 may simply be a family, with parents assuming the role of security administrator 150. The parents may wish to protect their children from undesirable content, such as pornography, adware, spyware, age-inappropriate content, advocacy for certain political, religious, or social movements, or forums for discussing illegal or dangerous activities, by way of non-limiting example. In this case, the parent may perform some or all of the duties of network administrator 150.

FIG. 1B is a block diagram disclosing a workload cluster 142 according to one or more examples of the present Specification. In this example, workload cluster 142 includes a rack mount chassis 144 which has installed therein a plurality of rack mount servers 146-1 through 146-N. Each rack mount server 146 may be a dedicated appliance, or may be configured with a hypervisor to launch one or more instances of a virtual client.

A switch 190 may be provided to communicatively couple workload cluster 142 to enterprise network 170. As described below, switch 190 may have a number of physical ports for communicatively coupling to rack mount servers 146. In an example, each server 146 has a physical wired connection, such as an Ethernet connection, to a single port of switch 190.

In some cases, some or all of rack mount servers 146-1 through 146-N are dedicated to providing a microcloud 160. Microcloud 160 may be a single purpose or dedicated cloud providing a particular service. For example, microcloud 160 may be configured to serve a website, provide communication systems such as one or more 4G LTE services, or any other appropriate service. In some cases, microcloud 160 is provided as a “tenant” on workload cluster 142. Workload cluster 142 may provide a virtual environment manager 164, which may be responsible for enforcing tenant boundaries between one or more microcloud tenants 160, and for dynamically provisioning virtual machines 162 as necessary. Virtual machines 162-1 through 162-N may represent a plurality of instances of a virtual server appliance. In some cases, VMs 162 may also be provided in different flavors. For example, some VMs 162 may be provisioned as firewalls, others may be provisioned as antivirus scanning appliance, and yet others may provide other auxiliary functions, in addition to VMs 162 provisioned as workload servers.

When switch 190 is provisioned with a load-balancing engine, the load-balancing engine is responsible for keeping track of the number and virtual IP (VIP) of workload servers, so that it can properly route traffic to the workload servers. In the case where each rack mount server 146 is a standalone appliance, switch 190 may maintain a table of the VIP of each rack mount server 146. In cases where workload servers are provided in a microcloud 160, switch 190 may provide a table that maps the VIP of each VM to a VIP assigned to the physical rack mount server 146 on which that VM 162 resides. Thus, switch 190 may include logic not only for routing the packet to the correct rack mount server 146, but also for directing the packet to the correct VM 162 on that rack mount server 146.

FIGS. 2A and 2B show examples of a system architecture for providing service appliances in a network environment, and specifically, providing service appliances as virtual line cards in a network switch. The virtual line card allows the service appliances to be located anywhere in the network, but other ways of providing the service appliance (e.g., directly connecting the service appliance on the switch) are also possible. It is noted that the examples are merely illustrative and are not intended to be limiting. Other architectures and configurations are envisioned by the disclosure.

FIG. 2A is a simplified schematic diagram illustrating a physical view of a system 110 for providing service appliances in a network environment. FIG. 2A includes a network (illustrated as multiple links 212) that connects one or more server farms 142-1 and 142-2 to one or more clients 110 via a cloud 210. Cloud 210 may encompass any public, semi-public, and/or private networks including enterprise networks, an Internet or intranet, community networks, etc. Individual servers in server farm 142-1 and 142-2 may communicate within the same farm via switches 240-1 and 240-2, respectively. Servers in server farm 142-1 may communicate with servers in server farm 142-2 via a switch 190 in this particular example implementation.

A service appliance 224 may connect to switch 190 over a communication channel 226 (e.g., over a port-channel). As used herein, a “communication channel” encompasses a physical transmission medium (e.g., a wire), or a logical connection (e.g., a radio channel, a network connection) used to convey information signals (e.g., data packets, control packets, etc.) from one or more senders (e.g., switch 190) to one or more receivers (e.g., service appliance 224). A communication channel, as used herein, can include one or more communication links, which may be physical (e.g., wire) or logical (e.g., data link, wireless link, etc.). Termination points of communication channels can include interfaces such as Ethernet ports, serial ports, etc. In embodiments of system 110, communication channel 226 may be a single channel: deployed for both control messages (i.e., messages that include control packets) and data messages (i.e., messages that include data packets).

As used herein, a “service appliance” is a discrete (and generally separate) hardware device or virtual machine with integrated software (e.g., firmware), designed to provide one or more network services including load balancing, firewall, intrusion prevention, virtual private network (VPN), proxy, etc. In some cases, switch 190 may be configured with an intelligent service card manager module (ISCM) 220, and service appliance 224 may be configured with a corresponding intelligent service card client module (ISCC) 230. ISCM 220 and ISCC 230 can form part of a Remote Integrated Service Engine (RISE) infrastructure for configuring service appliance 224 on the switch, e.g., as a virtual line card in switch 190.

FIG. 2B is a simplified schematic diagram illustrating a logical view of system 110. In some cases, ISCC 230 and ISCM 220 may be configured to allow service appliance 224 to appear as a virtual line card 290, or some other virtual network node/entity. The terms “line card” and “service module” are interchangeably used herein to refer to modular electronic circuits interfacing with telecommunication lines (such as copper wires or optical fibers) and that offer a pathway to the rest of a telecommunications network. Service appliance is often referred to simply as “appliance” or “module” herein. Hence, virtual line card 290 is interchangeable (in certain instances) with ISCM 220. A virtual service module (or a virtual line card) is a logical instance (of a service module) providing the same functionalities (as the service module). Service modules may perform various functions including providing network services (e.g., similar to service appliances). One difference between a service module and a service appliance is that the service module is physically located within a switch, for example, on an appropriate slot. Virtual service modules are similarly configurable within a switch.

In an example, RISE (or comparable technologies) allows (external) service appliances to connect to a switch and behave like a service module within a switch without having to take up a physical slot in the switch. RISE helps consolidate how the appliances are provisioned, and enables the appliances to have the benefits of being a service module within the switch. The task for provisioning and configuring of these service appliances is performed mostly by RISE being provided on the switch, making it easy for network administrators to add/remove service appliances in the network.

According to embodiments of the present disclosure, an appliance user can enjoy the same benefit of a service module's simple configuration and operation using the infrastructure of system 110. For example, setting up service appliance 224 for network configurations may be unnecessary. Substantially all such configurations may be made via switch 190, instead of service appliance 224. Service appliance 224 may offload (i.e., transfer) any network (e.g., L2/L3 network) specific control plane and data plane operations to switch 190. Data path acceleration that leverages an application specific integrated circuit (ASIC) (potentially embedded in switch 190) may also be possible in various embodiments. Switch 190 may communicate control messages to service appliance 224 over communication channel 226. Thus, configuration and provisioning of services within service appliance 224 may be implemented via switch 190.

Note that the numerical and letter designations assigned to the elements of FIGS. 2A and 2B do not connote any type of hierarchy; the designations are arbitrary and have been used for the purposes of teaching only. Such designations should not be construed in any way to limit their capabilities, functionalities, or applications in the potential environments that may benefit from the features of system 110. For ease of description, only two representative server farms are illustrated in FIGS. 2A and 2B. Any number of server farms and switches may be connected in the network without departing from the broad scope of the present disclosure.

For purposes of illustrating the techniques of system 110, it is important to understand the communications in a given system such as the system shown in FIGS. 2A and 2B. The following foundational information may be viewed as a basis from which the present disclosure may be properly explained. Such information is offered earnestly for purposes of explanation only and, accordingly, should not be construed in any way to limit the broad scope of the present disclosure and its potential applications.

Typically, network services such as load balancing, firewall, intrusion prevention, proxy, virtual private network (VPN), etc. are provided through one or more of the following options: (1) service appliances that connect to network switches and routers; (2) specially designed high-performance routers configured with the services; or (3) network devices such as routers or switches that are configured with service modules that provide the services.

Some service appliances (e.g., load balancers) integrate services such as load balancing, firewall, intrusion prevention, VPN, etc. in a single box format, which is generally based on modular, scalable platforms and which provides a cost-effective option of the three options listed previously. Service appliances may be connected externally to a switch (e.g., aggregate switch or access switch, etc.) via appropriate ports. Different service appliances are designed with specific features applicable to different network environments. The service appliances may be deployed independently to service-specific areas of the network infrastructure, or they may be combined for a layered approach. Service appliances are typically located between the clients and server farms. Data packets generally pass through the service appliances on the way to (and from) the servers/clients. The service appliances may be managed by a management application (e.g., software) on the service appliance that enables configuration settings and other management functions.

Specially designed high-performance routers may also provide network services. Such routers may implement a massive parallel processor hardware and software architecture to deliver integrated network services (e.g., firewall, deep packet inspection, etc.). Many of the functionalities are embedded in a specially designed processor in the router. For example, such a specially designed router can provide an integrated security solution (e.g., stateful packet filtering, intrusion detection and prevention, per-user authentication and authorization, VPN capability, extensive QoS mechanisms, multiprotocol routing, voice application support, and integrated WAN interface support) and routing in a single box.

Network services may also be integrated into a network device (such as a switch or router) using dedicated line cards. The line cards may be installed inside the device, allowing any port on the device to operate as a firewall port, while integrating the services inside the network infrastructure. Several line cards may be installed in the same chassis, providing a modular solution where needed. Such solutions permit the user to take advantage of existing switching and routing infrastructure without any costly upgrades.

Turning to the potential infrastructure of FIGS. 2A and 2B, the example network environment may be configured as one or more networks and, further, may be configured in any form including, but not limited to, local area networks (LANs), wireless local area networks (WLANs), virtual local area networks (VLANs), metropolitan area networks (MANS), wide area networks (WANs), VPNs, Intranet, Extranet, any other appropriate architecture or system, or any combination thereof that facilitates communications in a network. In some embodiments, a communication link may represent any electronic link supporting a LAN environment such as, for example, cable, Ethernet, wireless technologies (e.g., IEEE 802.11x), ATM, fiber optics, etc. or any suitable combination thereof. In other embodiments, communication links may represent a remote connection through any appropriate medium (e.g., digital subscriber lines (DSL), telephone lines, T1 lines, T3 lines, wireless, satellite, fiber optics, cable, Ethernet, etc. or any combination thereof) and/or through any additional networks such as a wide area networks (e.g., the Internet).

Elements of FIGS. 2A and 2B may be coupled to one another through one or more interfaces employing any suitable connection (wired or wireless), which provides a viable pathway for electronic communications. Additionally, any one or more of these elements may be combined or removed from the architecture based on particular configuration needs. System 110 may include a configuration capable of transmission control protocol/Internet protocol (TCP/IP) communications for the electronic transmission or reception of packets in a network. System 110 may also operate in conjunction with a user datagram protocol/IP (UDP/IP) or any other suitable protocol, where appropriate and based on particular needs. In addition, gateways, routers, switches, and any other suitable network elements may be used to facilitate electronic communication between various nodes in the network.

Switches in system 110, including switches 190, 240-1, and 240-2, may include any type of network element connecting network segments. For example, switches 190, 240-1, and 240-2 may include a multi-port network bridge that processes and routes data at a data link layer (Layer 2). In another example, switches 190, 240-1, and 240-2 may process data at a network layer (Layer 3), or Layer 4 (with network address translation and load distribution), or Layer 7 (load distribution based on application specific transactions), or at multiple layers (e.g., Layer 2 and Layer 3). In certain embodiments, functionalities of switches 190, 240-1, and 240-2 may be integrated into other network devices such as gateways, routers, or servers. In various embodiments, switches 190, 240-1, and 240-2 may be managed switches (e.g., managed using a command line interface (CLI), a web interface, etc.).

Communication channel 226 may include a port-channel, which can encompass an aggregation of multiple physical interfaces into one logical interface, for example, to provide higher aggregated bandwidth, load balancing and link redundancy. Communication channel 326 with multiple links can provide a high availability channel: if one link fails, traffic previously carried on this link can be switched to the remaining links. Communication channel 326 may contain up to 16 physical communication links and may span multiple modules for added high availability. In one embodiment, communication channel 326 can represent a port-channel with an aggregation of four point-to-point communication links over multiple ports. In another embodiment, communication channel 326 can represent a virtual port-channel (vPC).

Although FIGS. 2A and 2B show server farms 142-1 and 142-2, it should be appreciated that system 110 is not limited to servers. In fact, any network element may be connected to the network via appropriate switches, where these implementations may be based on particular needs. As used herein, the term “network element” is meant to encompass computers, virtual machines, network appliances, servers, routers, switches, gateways, bridges, load balancers, firewalls, processors, modules, or any other suitable device, component, proprietary element, or object operable to exchange information in a network environment. Moreover, the network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information. For example, server farms 142-1 and 142-2 may be replaced with LANs connecting desktop computers in a small office. In another example, server farms 142-1 and 142-2 may be replaced with a network of wireless communication devices. In yet another example, server farms 142-1 and 142-2 may be replaced with one or more supercomputers. Various other configurations and devices are contemplated within the broad framework of the present disclosure.

According to embodiments of the present disclosure, system 110 may provide for a fabric extender (FEX)-like protocol, auto-discovery, message transport service (MTS)-like control messages, and defined messages between service appliance 224 and switch 190. Configuration of service appliance 224 may be performed on switch 190 as for a line card. Data path forwarding may be offloaded to network line cards in switch 190. Control path processing may be offloaded to a supervisor engine on switch 190 as appropriate. In embodiments where service appliance 224 has multiple virtual services (e.g., virtual machines), each virtual service may be a separate virtual line card on switch 190.

FIG. 3 is a simplified block diagram illustrating example details of system 110 according to embodiments of the present disclosure. A supervisor engine 360 on switch 190 may communicate with service appliance 224 via a line card including a fabric port 362 that connects point-to-point to a node on service appliance 224. Supervisor engine 360 may include several modules such as an installer 364, an Ethernet port manager (ethPM) 366, a port-channel manager (PCM) 368, a Quality of Service (QoS) element 370, a route policy manager (RPM) 372, a unified/unicast routing information base (URIB) 374, an access control list manager (ACLmgr) 376, and a service policy manager (SPM) 378 for performing various routing and/or management functions. ISCM 220 may be provisioned in supervisor engine 360 to provide RISE related functionalities. ISCM 220 may manage one or more service modules, including in-chassis service modules and remote service modules.

In various embodiments, service appliance 224 may support stream control transmission protocol (SCTP) with various addresses (e.g., 127 addresses). In the absence of native SCTP support in supervisor engine 360, tunneling over UDP may be enforced to send SCTP packets. A Netstack module 380 may be provisioned in supervisor engine 360 for implementing TCP/IP stack for received frames hitting the control-plane of supervisor engine 360. Supervisor engine 360 may be configured with an inband port 352, which may be a virtual port that provides an interface for management traffic (such as auto-discovery) to a management processor such as a processor 386.

Each logical block disclosed herein is broadly intended to include one or more logic elements configured and operable for providing the disclosed logical operation of that block. As used throughout this Specification, “logic elements” may include hardware, external hardware (digital, analog, or mixed-signal), software, reciprocating software, services, drivers, interfaces, components, modules, algorithms, sensors, components, firmware, microcode, programmable logic, or objects that can coordinate to achieve a logical operation.

In various examples, a “processor” may include any combination of logic elements, including by way of non-limiting example a microprocessor, digital signal processor, field-programmable gate array, graphics processing unit, programmable logic array, application-specific integrated circuit, or virtual machine processor. In certain architectures, a multi-core processor may be provided, in which case processor 386 may be treated as only one core of a multi-core processor, or may be treated as the entire multi-core processor, as appropriate. In some embodiments, one or more co-processors may also be provided for specialized or support functions. In some examples, the processor is a programmable hardware device, which in this Specification expressly excludes a general-purpose CPU.

Load balancing engine 320, in one example, is operable to carry out computer-implemented methods as described in this Specification. Load balancing engine 320 may include one or more processors, and one or more non-transitory computer-readable mediums having stored thereon executable instructions operable to instruct a processor to provide load balancing. As used throughout this Specification, an “engine” includes any combination of one or more logic elements, of similar or dissimilar species, operable for and configured to perform one or more methods provided by load balancing engine 320. Thus, load balancing engine 320 may comprise one or more logic elements configured to provide methods as disclosed in this Specification. In some cases, load balancing engine 320 may include a special integrated circuit designed to carry out a method or a part thereof, and may also include software instructions operable to instruct a processor to perform the method. In some cases, load balancing engine 320 may run as a “daemon” process. A “daemon” may include any program or series of executable instructions, whether implemented in hardware, software, firmware, or any combination thereof, that runs as a background process, a terminate-and-stay-resident program, a service, system extension, control panel, bootup procedure, BIOS subroutine, or any similar program that operates without direct user interaction. In certain embodiments, daemon processes may run with elevated privileges in a “driver space,” or in ring 0, 1, or 2 in a protection ring architecture. It should also be noted that load balancing engine 320 may also include other hardware and software, including configuration files, registry entries, and interactive or user-mode software by way of non-limiting example.

In one example, load balancing engine 320 includes executable instructions stored on a non-transitory medium operable to perform a method according to this Specification. At an appropriate time, such as upon booting the device or upon a command from the operating system or a user, the processor may retrieve a copy of software from storage and load it into memory. The processor may then iteratively execute the instructions of load balancing engine 320 to provide the desired method.

In another example, load balancing engine 320 includes logic executed on an ASIC, FPGA, or other low-level hardware device specifically programmed to carry out the functions of load balancing engine 320. In one case, any portions of load balancing engine 320 that are not hard-coded into the logic may be loaded from a firmware or similar memory. In this case, load-balancing engine 320 may operate without the benefit of an operating system, to improve speed and efficiency.

Load balancing engine 320 may also communicatively couple to a TCAM 329. TCAM 329 may be configured to provide high-speed searching as disclosed herein.

According to various embodiments, ISCM 220 may offer various functionalities such as handling (i.e., accommodating, managing, processing, etc.) RISE messages (e.g., in MTS format), high availability activities, timer events, packet switch stream (PSS), American Standard Code for Information Interchange (ASCII) generation, logging, event handling, health monitoring, debugging, etc. ISCM 220 may be a finite state machine utility (FSMU) based application (e.g., which indicates an abstract machine that can be in one of a finite number of states). In various embodiments, ISCM 220 may have a well-defined MTS seamless authentication protocol (MTS SAP) assigned and it can open a socket-based MTS queue and bind to the well-defined SAP such that other processes may communicate with it.

In various embodiments, ISCM 220 may also maintain an array of MTS operation code (“opcode”), which can define how to process a received MTS message. The array may include per-opcode specific MTS flags, handler functions, etc. ISCM 220 may be configured to receive CLI driven MTS messages, MTS notifications (such as event driven messages indicating, for example, that a particular VLAN is up or down), and MTS request/responses. In various embodiments, ISCM 220 may be configured so that MTS-based communication with other processes may be non-blocking and asynchronous. Thus, ISCM 220 may handle multiple events (which can arrive at any time) for the same resource such that the state of the resource is consistent (and not compromised). A similar opcode can be provided even in non-MTS messages, which serves to indicate how a switch or a service can process the message.

After ports (e.g., appliance ports and switch ports) have been configured in RISE mode, ISCM 220 and ISCC 230 may perform auto-discovery and bootstrap to establish an appropriate control channel. After the control channel is established, applications in service appliance 224 may send control messages (e.g., using the UDP socket interface) to ISCC 230 through an application control plane 384. Application control plane 384 generally encompasses one or more software components for performing workflow management, self-management, and other application control layer processes. ISCC 230 may forward the control messages to ISCM 220 of switch 190 over communication channel 326. In example embodiments, ISCM 220 and ISCC 230 may communicate via UDP packets; however, various other protocols and formats may be accommodated by the teachings of the present disclosure. Supervisor 360 may be provisioned with (or have access to) processor 386 and a memory 388 for performing its various functions. ISCM 220 may use processor 386 and memory 388 to perform RISE related functions in switch 190. Similarly, service appliance 224 may be provisioned with (or have access to) a processor 390 and a memory 392. ISCC 230 may use processor 390 and memory 392 to perform RISE related functions in service appliance 224.

FIG. 4 is a block diagram of a routing table 400 according to one or more examples of the present Specification. In this example, four nodes are provided, designated node N0, N1, N2, and N3. Each node represents a server appliance having a unique VIP, whether a dedicated hardware server appliance or a virtual server appliance.

Load-balancing engine 320 designates 8 traffic buckets, labeled B0, B1, B2, B3, B4, B5, B6, and B7. Based on load and demand, load-balancing engine 320 maps each traffic bucket to an appropriate node. In this example, buckets B0 and B4 are mapped to node NO. Buckets B1 and B5 are mapped to node N1. Buckets B2 and B6 are mapped to node N2. Buckets B3 and B7 are mapped to node N3. These mappings are provided by way of nonlimiting example only, and are provided strictly to illustrate the principle of mapping buckets to nodes.

When switch 190 receives incoming traffic, load-balancing engine 320 operates to execute an appropriate algorithm for assigning the incoming traffic to a traffic bucket. This may include, for example, random or pseudorandom assignment, round robin scheduling, or any suitable scheduling algorithm. In one example, an algorithm may be based on the source IP address of the incoming packet, as described in more detail in connection with FIGS. 7 and 8.

After assigning the traffic to a bucket, switch 194 modifies the packet with the appropriate VIP for the node servicing that bucket, and forwards the packet.

When a response comes, switch 194 modifies the packet to reflect the publically visible IP address of switch 194, so that the load balancing is completely invisible to external hosts.

FIG. 5 is a flowchart of an example method 500 performed by load-balancing engine 320 according to one or more examples of the present Specification.

In block 510, switch 190 receives incoming traffic and provides the incoming traffic to load-balancing engine 320.

In block 520, switch 190 compares the destination IP of the incoming traffic to the VIP designated for load balancing. If there is a match, the incoming traffic is provided to load balancing engine 320 for load balancing. If not, then switch 190 simply routes or switches the traffic according to its normal function.

In block 530, load-balancing engine 320 assesses workload balance for available workload servers. As described above, this may be performed via round-robin assignment, random or pseudo-random assignment, or any other suitable load balancing algorithm.

In block 540, load-balancing engine 320 identifies the best available node for servicing the incoming traffic, based on the assessing of block 530.

In block 550, according to the identifying of block 540, load-balancing engine 320 assigns the incoming traffic to a bucket associated with the best available node. Assigning to a node may comprise modifying the header to reflect the VIP for the assigned node.

In block 570, after load-balancing engine 320 has assigned the traffic to an appropriate bucket and thereby to an appropriate node, switch 190 forwards the incoming traffic to the node designated for servicing that bucket, specifically by forwarding the traffic to the appropriate VIP.

In block 580, load-balancing engine 320 may log the transaction, as appropriate or necessary.

In block 590, the method is done.

FIG. 6 illustrates a method of performing load balancing on a switch with the aid of a TCAM, such as TCAM 329 according to one or more examples of the present Specification. This example employs the notion of a flow. In an example, a flow is uniquely identified by a tuple T, comprising src-ip (source IP address), dst-ip (destination IP address), protocol, L4-src-port (layer 4 source port) and L4-dst-port (layer 4 destination port).

In an example, a client device 110-1 sends a packet directed to a VIP serviced by switch 190. By way of illustration, this flow is referred to as F1, and tuple T1 identifies flow F1. Tuple T1 comprises (Dev-110-1-IP, VIP, TCP, L4-src-port, L4-dest-port).

Similarly client device 110-2 initiates traffic to the same VIP. Since client 110-2's IP address is different from client 110-1's, this flow will have a different Tuple. By way of illustration, this is referred to as flow F2, identified by tuple T2. Tuple T2 comprises (Dev-110-2-IP, VIP, TCP, L4-src-port, L4-dest-port).

In various examples, sets of buckets may be part of a “pool,” and one or more pools can be assigned to a single VIP, allowing VIP traffic to be load balanced among server nodes.

Referring now to method 600 in FIG. 6, it is assumed that switch 190 has now received flows F1 and F2.

In block 610, TCAM 329 looks up the IP address of VIP as it appears in both flows. In this example, both flows are directed to VIP, which is a virtual IP address for a service provided by servers in workload cluster 142. Thus, switch 190 can quickly determine that flows F1 and F2 are to be load balanced.

In block 620, load balancing engine 320 assigns each node to a traffic bucket as described herein. In certain examples, this may be accomplished by any of the load balancing algorithms disclosed herein, or by any other appropriate load balancing algorithm. In one example, assigning each flow to a bucket comprises assigning according to method 900 of FIG. 9, based on Dev-110-1-IP and Dev-110-2-IP respectively. In that case, TCAM 329 may include a table mapping masked IP address fragments to traffic buckets.

In block 640, load balancing engine 320 assigns each flow to a node for servicing, such as a workload server in workload cluster 142. This may be a deterministic assignment based on the traffic bucket that each flow was assigned to. For increased speed, this may also be performed using TCAM 329. For example, TCAM 329 may include a table mapping traffic buckets to service nodes.

In block 660, load balancing engine 320 rewrites the L2 header for the incoming packets. For example, assuming that flow F1 was assigned to service node 1 in workload cluster 142, and flow F2 was assigned to service node 2 in workload cluster 142, load balancing engine 320 rewrites the L2 headers for the packets in those flows to direct them to their respective service nodes.

In block 680, switch 190 is finished with its load balancing tasks, and now acts as a switch, switching or routing the packets to the nodes provided by their new L2 headers.

Blocks 610 through 680 are repeated for each incoming packet, with an appropriate bucket and service node being selected for each. Assuming a well-configured load balancing engine 320, packets will be well distributed across available service nodes in workload cluster 142 so that workload is optimally distributed across available service nodes.

Reverse traffic (response from service nodes to client devices) are delivered directly to the respective clients without any intervention from load balancing engine 320.

In Block 690 the method is done.

FIG. 7 is a block diagram view 700 of method 600 as described in FIG. 6.

FIG. 8 is a block diagram of a leaf-spine network 800 according to one or more examples of the present Specification. The adaptive load balancing teachings of the present Specification are well-suited to leaf-spine networks, though they are also compatible with older three-tier “tree” architectures.

In contrast to the three-layer “tree” architecture, leaf-spine has only two layers: a leaf layer and a spine layer. In the example of FIG. 8, switch 190 is shown as a spine switch, while additional leaf switches 390 are also shown. To illustrate the principle, one spine switch 190 and four leaf switches 390 are shown in this FIGURE. In a deployed network, the number of spine switches 190 and leaf switches 390 will be determined by the configuration and demands of the network.

All devices in leaf-spine network 800 are the same number of segments away, and have a consistent latency. The leaf layer of leaf-spine network 800 may include leaf switches 390 that connect to terminal devices such as servers, or intermediate devices such as edge routers, firewalls, security devices, or any other suitable device. The spine layer, comprising one or more spine switches 190, interconnects each leaf switch 390 with each other leaf switch 390, and also connects leaf switches 390 to other spine switches 190. While generally applicable as a routing topology, leaf-spine is especially useful in data centers, where there is a focus on data traveling between nodes in a single network (rather than, for example, data traveling outside of the network). Specific embodiments of leaf-spine include “Transparent Interconnection of Lots of Links” (TRILL) or “shortest path bridging” (SPB). Both Trill and SPB may determine where are connected to the fabric so as to provide a loop-free, shortest path to their respective Ethernet MAC addresses

In an example of a leaf-spine architecture, three-layer routing may be used to interconnect the layers. This may enable the predictable latency discussed above. Dynamic routing may also be used to determine the best path between nodes. In certain embodiments, routes may be adjusted based on changes in the network. In an embodiment, routes may be configured via “Equal-Cost Multipathing” (ECMP). Advantageously, with ECMP, a plurality of connections can remain active, and network loops can be avoided.

Certain embodiments of leaf-spine may also make it easier to add, upgrade, replace, or otherwise reconfigure hardware with minimal network disruptions. In an example, an additional spine switch can easily be added to the network, and then necessary uplinks can be added to each leaf switch. This seamlessly provides additional interlayer bandwidth. Similarly, when additional port capacity is needed, additional leaf switches 390 can be added. These are communicatively coupled to every spine in the network. For example, leaf-spine network may provide a fabric such as Cisco® Standalone Fabric.

In the example of FIG. 8, spine switch 190 includes a load balancing engine 320, as well as a dynamic hostname configuration protocol (DHCP) server 840. DHCP server 840 is to dynamically assign a hostname and/or IP address to each new node that appears in the network. In this case, certain IP addresses may be reserved in certain “pools,” so that nodes in those pools can be recognized as belonging to the pool. A network manager 370 and orchestrator 380 are also provided. Network manager 370 may be any suitable device, such as a Cisco® Prime Data Center Network Manager (DCNM) or similar. Orchestrator 380 may be a suitable network orchestrator, such as Cisco® Unified Computing System Director (UCSD), VMWare vCD, or OpenStack, by way of nonlimiting example.

By way of example, addresses of the form 10.10.14.X are reserved for web servers in web server pool 810. Addresses of the form 10.10.18.X are reserved for e-mail servers in e-mail server pool 820. Addresses of the form 10.10.24.X are reserved for file servers in file server pool 830.

In the above example, 256 contiguous addresses are reserved for each class of servers. For example, all addresses of the range 10.10.14.0-10.10.14.255 belong to web server pool 810. However, it should be recognized that any suitable number of addresses may be allocated to a pool, and the addresses need not be contiguous.

As described above, load balancing engine 320 is concerned with fast load balancing of traffic. For example, traffic coming in on virtual IP address (VIP) 10.10.0.6 is directed to web server pool 810. Thus, when spine switch 190 receives a packet with 10.10.0.6 in the destination field, it load balances the traffic, assigns it to one of the servers in web server pool 810, and then forwards the packet to leaf switch 390-1, which forwards the packet to a server in web server pool 810.

However, in a dynamic virtualized data center, it may be understood that the servers in web server pool 810 may not be individual “bare metal” servers. Rather, they may be VMs that are dynamically provisioned as needed to meet demand. In times of increased demand, new VMs may be “spun up” and added to web server pool 810. Once the period of high demand has subsided, those extra VMs may be “spun down,” so that those resources can be dedicated to other purposes.

Thus, it is advantageous if the configuration of load balancing engine 320 can be made “touchless.” In other words, a network administrator 150 would like to be able to use management console 140 to specify a configuration, such as via network manager 370 and orchestrator 380, so that when orchestrator 380 adds a new network node, network manager 370 automatically reconfigures load balancing engine 320 with appropriate rules updates without further intervention from network administrator 150.

A method for achieving this result is described in the flow charts of FIGS. 9, 10, and 11. These flow charts should be understood to be nonlimiting examples of the method provided in this Specification. Any of the operations disclosed in these flow charts may be performed in any appropriate order, and additional operations may be added or omitted as appropriate.

FIG. 9 is a flow chart of a method 900 that may be used to configure network manager 370 to provide adaptive load balancing according to one or more examples of the present Specification.

In block 910, a user such as network administrator 150 creates a new tenant via orchestrator 380 that maps to an appropriate organization and partition in the fabric of spine-leaf network 300.

In block 920, appropriate information is populated in network manager 370, such as in a lightweight directory access protocol (LDAP) database. In one example, the data may be populated directly from orchestrator 380 via appropriate application programming interfaces (APIs), such as representational state transfer (REST) APIs. Alternatively, network administrator 150 may directly populate the database via an interface of network manager 370, such as a graphical user interface (GUI).

In block 930, network administrator 150 may select one or more switches 190 on which to enable the ITD feature. Based on load balancing requirements, network administrator 140 may create the ITD service, appropriate virtual IPs (VIPs) for routing to desired services, incoming interfaces for load balancing, and necessary device groups, such as webserver pool 810, email server pool 820, or file server pool 830. Device group membership may be dynamically populated based on real-time network conditions. ITD configuration can be created via “Power On Auto Provisioning” (POAP), or invoking configuration commands directly via CLI or GUI/REST API provided by network manager 370. However, network administrator 150 does not want to have to reconfigure the ITD service with each new virtual device that is spun up. Thus, this Specification provides for automated adaptive load balancing.

In block 940, orchestrator 340 creates a tenant network, for which it allocates an appropriate layer 2 segment ID from an orchestrator-managed segment ID pool. Orchestrator 340 may also send this information to network manager 370 via REST API calls so that it is populated into network manager 370's LDAP network repository to be available for subsequent query from leaf switches 390.

In block 950, network administrator 150 selects a network profile as part of network creation. This allows network administrator 150 to designate whether the network should be part of an ITD load balancing topology, including whether to associate the entire network or subset (range). Network administrator 150 may also provide an ITD device-group name to be associated with the network.

In block 960, as part of the network creation, orchestrator 380 programs the virtual infrastructure. Specifically, orchestrator 380 programs switch 190 with a port profile having a layer 2 segment ID that it allocated for the previously-created tenant network.

In block 980, network administrator 150 may create via orchestrator 380, within switch 190, an appropriate port group (such as in the hypervisor), which is pushed compute nodes that are part of a virtual Ethernet module.

In block 999 the method is done.

FIG. 10 is a flow chart of a method of provisioning dynamic load balancing according to one or more examples of the present Specification.

In block 1010, a new virtual machine spins up and attaches to a port group, such as the port group provisioned in block 970 of FIG. 9. This virtual machine can be a service appliance that needs to be part of cluster for which ITD is providing load balancing services.

In block 1020, leaf switch 390 detects the new host. In a dynamic fabric automation (DFA) environment, a leaf switch can detect the presence of a new virtual or physical host by various means, including by way of nonlimiting example:

A data packet trigger may be based on a new media access control (MAC) triggered by an incoming IEEE 8002.1Q-tagged packet, which may be any suitable packet, including ARP, DHCP, or ND by way of nonlimiting example. Leaf switch 390 pulls down the associated network configuration profile network manager 380, for example using the VLAN-ID and the mobility domain as the query identifier.

An orchestrator 380 utility, such as vSphere data protection (VDP) may be used to trigger automatic configuration based on the segment ID. When the VM is coming up, the hypervisor virtual switch may send out a notification to the leaf switch, with notification of a workload coming up in “Segment X,” and requesting allocation of whatever resources are necessary to be ready to accept traffic from this VM. Leaf switch 390 may then pull down the associated network configuration profile from network manager 370 using the segment ID as a query identifier.

In block 1040, leaf switch 390 queries network manager 380 with the layer 2 Segment ID or VLAN-ID and mobility domain as the query identifier.

In block 1050, as part of the query response, network manager 380 returns to leaf switches 390 the required information, including for example a virtual routing and forwarding (VRF) instance, layer 3 segment ID, IP address, and profile. These may be used to instantiate the end-host (virtual) network profile configuration.

In decision block 1070, a leaf switch 390 inspects IP address of a new host to determine whether it needs to be part of an ITD service group. As indicated earlier, an entire network or range/subset can be configured to be part of a service group (see, e.g., FIG. 8). If not, then no further action needs to be taken and in block 1099 the method is done.

If the new host is to be added to the ITD device group, then in block 1080, leaf switch 390 caches ITD service group information associated with the appropriate network. Thus, the next time a new host in the same network gets detected on leaf switch 390, leaf switch 390 can apply an appropriate ITD service load balancing policy without querying the LDAP database of network manager 370. This efficiently keeps the configuration up-to-date, as configuration can be performed at the source switch without manual intervention or additional handshakes with network manager 370.

In block 1099, the method is done.

FIG. 11 is a flow chart of a method of automatically removing a node from an ITD pool according to one or more examples of the present Specification.

In block 1110, the host is powered down, communication with it is lost, or it is otherwise no longer associated with leaf switch 390.

In block 1180, leaf switch 390 cleans up the configuration. For example, if the host is part of an ITD service group, it is removed from that ITD service group. ITD can then adjust its “buckets” to adjust for the loss of the node.

In block 1199, the method is done.

Note that in this Specification, references to various features (e.g., elements, structures, modules, components, steps, operations, characteristics, etc.) included in “one embodiment”, “example embodiment”, “an embodiment”, “another embodiment”, “some embodiments”, “various embodiments”, “other embodiments”, “alternative embodiment”, and the like are intended to mean that any such features are included in one or more embodiments of the present disclosure, but may or may not necessarily be combined in the same embodiments. Furthermore, the words “optimize,” “optimization,” and related terms are terms of art that refer to improvements in speed and/or efficiency of a specified outcome and do not purport to indicate that a process for achieving the specified outcome has achieved, or is capable of achieving, an “optimal” or perfectly speedy/perfectly efficient state.

In example implementations, at least some portions of the activities outlined herein may be implemented in software, for example, provisioned in service appliance 224 and/or switch 190 (e.g., through various modules, algorithms, processes, etc.). In some embodiments, one or more of these features may be implemented in hardware, provided external to these elements, or consolidated in any appropriate manner to achieve the intended functionality. Service appliance 224 and/or switch 190 may include software (or reciprocating software) that can coordinate in order to achieve the operations as outlined herein. In still other embodiments, these elements may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof.

Furthermore, switch 190 and service appliance 224 described and shown herein (and/or their associated structures) may also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. Additionally, some of the processors and memories associated with the various network elements may be removed, or otherwise consolidated such that a single processor and a single memory location are responsible for certain activities. In a general sense, the arrangements depicted in the FIGURES may be more logical in their representations, whereas a physical architecture may include various permutations, combinations, and/or hybrids of these elements. It is imperative to note that countless possible design configurations can be used to achieve the operational objectives outlined here. Accordingly, the associated infrastructure has a myriad of substitute arrangements, design choices, device possibilities, hardware configurations, software implementations, equipment options, etc.

In some of the example embodiments, one or more memories (e.g., memory 392, memory 388) can store data used for the operations described herein. This includes the memory being able to store instructions (e.g., as part of logic, software, code, etc.) that are executed to carry out the activities described in this Specification. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, processor 386 and processor 390 could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM)), an ASIC that includes digital logic, software, code, electronic instructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types of machine-readable mediums suitable for storing electronic instructions, or any suitable combination thereof.

In operation, components in system 110 can include one or more memory elements (e.g., memory 388, memory 392) for storing information to be used in achieving operations as outlined herein. These devices may further keep information in any suitable type of non-transitory storage medium (e.g., random access memory (RAM), read only memory (ROM), field programmable gate array (FPGA), erasable programmable read only memory (EPROM), electrically erasable programmable ROM (EEPROM), etc.), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. The information being tracked, sent, received, or stored in system 110 could be provided in any database, register, table, cache, queue, control list, or storage structure, based on particular needs and implementations, all of which could be referenced in any suitable timeframe. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’

It is also important to note that the operations and steps described with reference to the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, the system. Some of these operations may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the discussed concepts. In addition, the timing of these operations may be altered considerably and still achieve the results taught in this disclosure. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by the system in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the discussed concepts.

Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. For example, although the present disclosure has been described with reference to particular communication exchanges involving certain network access, formatting, and protocols, system 110 may be applicable to other exchanges, formats, or routing protocols. Moreover, although system 110 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements, and operations may be replaced by any suitable architecture or process that achieves the intended functionality of system 110.

Computer program logic implementing all or part of the functionality described herein is embodied in various forms, including, but in no way limited to, a source code form, a computer executable form, and various intermediate forms (for example, forms generated by an assembler, compiler, linker, or locator). In an example, source code includes a series of computer program instructions implemented in various programming languages, such as an object code, an assembly language, or a high-level language such as OpenCL, Fortran, C, C++, JAVA, or HTML for use with various operating systems or operating environments. The source code may define and use various data structures and communication messages. The source code may be in a computer executable form (e.g., via an interpreter), or the source code may be converted (e.g., via a translator, assembler, or compiler) into a computer executable form.

In one example embodiment, any number of electrical circuits of the FIGURES may be implemented on a board of an associated electronic device. The board can be a general circuit board that can hold various components of the internal electronic system of the electronic device and, further, provide connectors for other peripherals. More specifically, the board can provide the electrical connections by which the other components of the system can communicate electrically. Any suitable processors (inclusive of digital signal processors, microprocessors, supporting chipsets, etc.), memory elements, etc. can be suitably coupled to the board based on particular configuration needs, processing demands, computer designs, etc. Other components such as external storage, additional sensors, controllers for audio/video display, and peripheral devices may be attached to the board as plug-in cards, via cables, or integrated into the board itself. In another example embodiment, the electrical circuits of the FIGURES may be implemented as stand-alone modules (e.g., a device with associated components and circuitry configured to perform a specific application or function) or implemented as plug-in modules into application specific hardware of electronic devices.

Note that with the numerous examples provided herein, interaction may be described in terms of two, three, four, or more electrical components. However, this has been done for purposes of clarity and example only. It should be appreciated that the system can be consolidated in any suitable manner. Along similar design alternatives, any of the illustrated components, modules, and elements of the FIGURES may be combined in various possible configurations, all of which are clearly within the broad scope of this Specification. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of electrical elements. It should be appreciated that the electrical circuits of the FIGURES and its teachings are readily scalable and can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of the electrical circuits as potentially applied to a myriad of other architectures.

By way of nonlimiting example, there is disclosed a network apparatus for providing native load balancing within a switch, comprising: a first network interface operable to communicatively couple to a first network; a plurality of second network interfaces operable to communicatively couple to a second network; one or more logic elements comprising a switching engine operable for providing network switching; and one or more logic elements comprising a load balancing engine operable for: receiving incoming network traffic via the first network; and assigning the incoming traffic to a traffic bucket associated with the second network; wherein the switching engine and load balancing engine are configured to be provided on the same hardware as each other and as the first network interface and plurality of second network interfaces.

There is disclosed in an example, a network apparatus for providing native load balancing within a switch, comprising: a first network interface operable to communicatively couple to a first network; a plurality of second network interfaces operable to communicatively couple to a second network, the second network comprising a service pool of service nodes; one or more logic elements comprising a switching engine operable for providing network switching; one or more logic elements comprising a load balancing engine operable for: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration; detecting a new service node added to the service pool; and adjusting the load balancing configuration to account for the new service node; wherein the switching engine and load balancing engine are configured to be provided on the same hardware as each other and as the first network interface and plurality of second network interfaces.

There is further disclosed an example, wherein the network apparatus is a switch.

There is further disclosed an example, wherein the switch is a leaf switch in a spine-leaf architecture.

There is further disclosed an example, wherein adjusting the load balancing configuration comprises determining that configuration data are not cached, and querying a network manager apparatus for configuration data.

There is further disclosed an example, wherein adjusting the load balancing configuration further comprises caching the configuration data.

There is further disclosed an example, wherein adjusting the load balancing configuration comprises determining that configuration data are cached, and using the cached configuration data.

There is further disclosed an example, wherein the native hardware comprises a ternary content addressable memory (TCAM).

There is further disclosed in an example, a method of providing native load balancing within a switch, comprising: communicatively coupling to a first network via a first network interface; communicatively coupling to a second network via a plurality of second network interfaces, the second network comprising a service pool of service nodes; providing network switching; providing load balancing, comprising: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration; detecting a new service node added to the service pool; and adjusting the load balancing configuration to account for the new service node.

There is further disclosed an example, wherein providing network switching comprises providing leaf switch functionality in a spine-leaf architecture.

There is further disclosed an example, wherein adjusting the load balancing configuration comprises determining that configuration data are not cached, and querying a network manager apparatus for configuration data.

There is further disclosed an example, wherein adjusting the load balancing configuration further comprises caching the configuration data.

There is further disclosed an example, wherein adjusting the load balancing configuration comprises determining that configuration data are cached, and using the cached configuration data.

There is further disclosed an example, wherein load balancing incoming network traffic comprises querying an on-device ternary content addressable memory (TCAM).

There is further disclosed in an example, one or more tangible, non-transitory computer-readable storage mediums having stored thereon executable instructions for instructing a processor for: communicatively coupling to a first network via a first network interface; communicatively coupling to a second network via a plurality of second network interfaces, the second network comprising a service pool of service nodes; providing network switching; providing load balancing, comprising: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration; detecting a new service node added to the service pool; and adjusting the load balancing configuration to account for the new service node.

There is further disclosed an example, wherein providing network switching comprises providing leaf switch functionality in a spine-leaf architecture.

There is further disclosed an example, wherein adjusting the load balancing configuration comprises determining that configuration data are not cached, and querying a network manager apparatus for configuration data.

There is further disclosed an example, wherein adjusting the load balancing configuration further comprises caching the configuration data.

There is further disclosed an example, wherein adjusting the load balancing configuration comprises determining that configuration data are cached, and using the cached configuration data.

There is further disclosed an example, wherein load balancing incoming network traffic comprises querying an on-device ternary content addressable memory (TCAM).

There is further disclosed an example, wherein the medium comprises a native medium of a network switch.

There is further disclosed an example of a method comprising performing the operations disclosed in any of the preceding examples.

There is further disclosed an example of one or more non-transitory computer-readable mediums having stored thereon executable instructions for performing the method or the operations of any of the preceding examples.

There is further disclosed an example comprising means for performing the method, or operating the computer-readable medium of any of the preceding examples.

There is further disclosed an example wherein the means comprise a processor and a memory.

Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “steps for” are specifically used in the particular claims; and (b) does not intend, by any statement in the Specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims. 

What is claimed is:
 1. A network switch for providing native load balancing, the network switch comprising: a first network interface operable to communicatively couple to a first network; a plurality of second network interfaces operable to communicatively couple to a second network associated with a layer 2 segment identifier, the second network comprising a service pool of service nodes; a switching engine comprising programmable hardware operable for providing network switching; and a load balancing engine comprising programmable hardware operable for: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration, wherein the native hardware enables the load balancing engine to load balance packets in the network traffic without passing the packets to a higher level of a network stack by rewriting a layer 2 header of the packets; detecting a new service node on the second network; querying a network manager with the layer 2 segment identifier associated with the second network; receiving a response from the network manager, the response including network configuration data for the new service node; determining that the new service node is in the service pool based on the network configuration data; and adjusting the load balancing configuration to account for the new service node; wherein the switching engine and load balancing engine are provided on the same programmable hardware with the first network interface and plurality of second network interfaces.
 2. The network switch of claim 1, wherein the network switch is a leaf switch in a spine-leaf architecture.
 3. The network switch of claim 1, wherein adjusting the load balancing configuration comprises determining that configuration data are not cached, and querying a network manager apparatus for configuration data.
 4. The network switch of claim 3, wherein adjusting the load balancing configuration further comprises caching the configuration data.
 5. The network switch of claim 1, wherein adjusting the load balancing configuration comprises determining that configuration data are cached, and using the cached configuration data.
 6. The network switch of claim 1, wherein the native hardware comprises a ternary content addressable memory (TCAM).
 7. The network switch of claim 1, wherein the programmable hardware comprises one or more Application Specific Integrated Circuits (ASICs) configured to run the switching engine and the load balancing engine.
 8. A method of providing native load balancing within a switch, comprising: communicatively coupling to a first network via a first network interface; communicatively coupling to a second network via a plurality of second network interfaces, the second network comprising a service pool of service nodes; providing network switching; and providing load balancing, comprising: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration, wherein the native hardware enables load balancing packets in the incoming network traffic without passing the packets to a higher level of a network stack by rewriting a layer 2 header of the packets; detecting a new service node on the second network; querying a network manager with a layer 2 segment identifier associated with the second network; receiving a response from the network manager, the response including network configuration data for the new service node; determining that the new service node is in the service pool based on the network configuration data; and adjusting the load balancing configuration to account for the new service node.
 9. The method of claim 8, wherein providing network switching comprises providing leaf switch functionality in a spine-leaf architecture.
 10. The method of claim 8, wherein adjusting the load balancing configuration comprises determining that configuration data are not cached, and querying a network manager apparatus for configuration data.
 11. The method of claim 10, wherein adjusting the load balancing configuration further comprises caching the configuration data.
 12. The method of claim 8, wherein adjusting the load balancing configuration comprises determining that configuration data are cached, and using the cached configuration data.
 13. The method of claim 8, wherein load balancing incoming network traffic comprises querying an on-device ternary content addressable memory (TCAM).
 14. One or more tangible, non-transitory computer-readable storage mediums having stored thereon executable instructions for instructing a processor for: communicatively coupling to a first network via a first network interface; communicatively coupling to a second network via a plurality of second network interfaces, the second network comprising a service pool of service nodes; providing network switching; and providing load balancing, comprising: load balancing incoming network traffic to the service pool via native hardware according to a load balancing configuration, wherein the native hardware enables load balancing packets in the incoming network traffic without passing the packets to a higher level of a network stack by rewriting a layer 2 header of the packets; detecting a new service node on the second network; querying a network manager with a layer 2 segment identifier associated with the second network; receiving a response from the network manager, the response including network configuration data for the new service node; determining that the new service node is in the service pool based on the network configuration data; and adjusting the load balancing configuration to account for the new service node.
 15. The one or more tangible, non-transitory computer-readable mediums of claim 14, wherein providing network switching comprises providing leaf switch functionality in a spine-leaf architecture.
 16. The one or more tangible, non-transitory computer-readable mediums of claim 14, wherein adjusting the load balancing configuration comprises determining that configuration data are not cached, and querying a network manager apparatus for configuration data.
 17. The one or more tangible, non-transitory computer-readable mediums of claim 16, wherein adjusting the load balancing configuration further comprises caching the configuration data.
 18. The one or more tangible, non-transitory computer-readable mediums of claim 14, wherein adjusting the load balancing configuration comprises determining that configuration data are cached, and using the cached configuration data.
 19. The one or more tangible, non-transitory computer-readable mediums of claim 14, wherein load balancing incoming network traffic comprises querying an on-device ternary content addressable memory (TCAM).
 20. The one or more tangible, non-transitory computer-readable mediums of claim 14, wherein the medium comprises a native medium of a network switch. 